-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tenders and contracts lists pages for Dashboards module #3053
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey! It looks great, just a few details (they can be fixed here or open a new issue if you prefer):
-
format the prices with locale separators and units. You can check how it's been implemeted in Mataro investments
-
if I'm in a contract or a tender, I'd expect the navigation option to be active:
- data should be sorted by date ASC. You can't trust it will be sorted in the CSV
- in contracts item page add the disccount %. Anyway I'm creating a new issue with more columns we could display to make it more interesting
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are two CSV files commited, is that right?
app/javascript/gobierto_dashboards/modules/contracts_controller.js
Outdated
Show resolved
Hide resolved
@@ -0,0 +1,8 @@ | |||
export const store = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ferblape Rethink if we should redeclare all this kind of things by module
a146709
to
981efb9
Compare
@ferblape since there is a new issue for the new columns, I'll do the last thing there if that's ok! The other things you mentioned are now fixed. Routing and nav are not great atm though. I'll redo them after I talk with @Crashillo. |
@@ -0,0 +1,12 @@ | |||
export const contractsColumns = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we move the columns to the module configuration JSON?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this JSON config already available from de API? Our initial idea was fetch the site metadata from XHR call (because it should be stored in DB), instead having a json config file in the code
264f8d7
to
bc1b444
Compare
- Renaming routes to the Spanish equivalents - Removing "tenders" route since it's actually inside "contracts". - Removing index route because it won't be neccessary
And removing them from data()
…(contract show and tender show)
Fixing specs too, since the default order changed and now everything is properly formatted.
5bc9733
to
8901ed9
Compare
Things left to be done in other issues:
@ferblape if everything else is correct I'll merge it |
@ferblape is the review finished? can I merge it? |
Yep 🚀 |
Wait wait wait |
Blat the Kid, the fastest merge on this side of the Mississipi |
app/javascript/gobierto_dashboards/modules/contracts_controller.js
Outdated
Show resolved
Hide resolved
app/javascript/gobierto_dashboards/webapp/components/TableRow.vue
Outdated
Show resolved
Hide resolved
app/javascript/gobierto_dashboards/webapp/containers/contract/ContractsIndex.vue
Show resolved
Hide resolved
To avoid using _self as this. Also (not related), adding destructuring.
@Crashillo I think everything is either done or postponed (:P), can you check again? |
{ path: "/dashboards/contratos", component: Home, | ||
children: [ | ||
{ path: "resumen", name: "summary", component: Summary }, | ||
{ path: "contratos", name: "contracts_index", component: ContractsIndex }, | ||
{ path: "contratos/:id", name: "contracts_show", component: ContractsShow }, | ||
{ path: "licitaciones", name: "tenders_index", component: TendersIndex }, | ||
{ path: "licitaciones/:id", name: "tenders_show", component: TendersShow }, | ||
] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@eltercero Don't you tell me you gonna add the props here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but I'll do it in the latest issue on development to avoid conflicts in three separate branches #3053 (comment)
Closes #2997
✌️ What does this PR do?
Integrates the markup done is #3028 with the remote csv data defined in Gobierto Dashboard settings. This PR enables several new pages for Contracts and Tenders dashboard in the main site:
Some parts, like the filters and the summary, are empty on purpose since this is still a work in progress.
Navigation should work between main parts (Summary ,Tenders and Contracts) and within the details page of every contract/tender.
🔍 How should this be manually tested?
It's available in staging: https://burjassot.gobify.net/dashboards/contratos/resumen
👀 Screenshots
.env.example
?config/application.yml
?config/secrets.yml
?(Changes in these files might need to update the role in Ansible)
📖 Does this PR require updating the documentation?