Skip to content

Add available services to meetings#3150

Merged
oriolgual merged 7 commits intomasterfrom
feature/meeting_services
Apr 19, 2018
Merged

Add available services to meetings#3150
oriolgual merged 7 commits intomasterfrom
feature/meeting_services

Conversation

@rbngzlv
Copy link
Copy Markdown
Contributor

@rbngzlv rbngzlv commented Apr 8, 2018

🎩 What? Why?

The admin can define what services will be available in the meeting (simultaneous translation, space enabled for people with functional diversity, children's area, ...)

📌 Related Issues

📋 Subtasks

  • Add specs
  • Add CHANGELOG entry

📷 Screenshots (optional)

screen shot 2018-04-18 at 18 41 45

@ghost ghost assigned rbngzlv Apr 8, 2018
@ghost ghost added the status: WIP label Apr 8, 2018
@xabier xabier mentioned this pull request Apr 8, 2018
16 tasks
@rbngzlv rbngzlv mentioned this pull request Apr 8, 2018
8 tasks
@rbngzlv rbngzlv force-pushed the feature/meeting_services branch from ff8914d to 37885b7 Compare April 8, 2018 15:46
@rbngzlv
Copy link
Copy Markdown
Contributor Author

rbngzlv commented Apr 10, 2018

@decidim/lot-core, @deivid-rodriguez I have duplicated three javascripts files from the surveys component to make the following UI in the admin.

screen shot 2018-04-10 at 16 14 23

I think this javascripts are valid for any nested resource, I'm right? If yes, what do you think about moving this files to the admin component?

@deivid-rodriguez
Copy link
Copy Markdown
Contributor

@rbngzlv They were definitely developed with reusability in mind! :) I agree with moving them to decidim-admin instead of copying the files 👍

@rbngzlv rbngzlv force-pushed the feature/meeting_services branch 3 times, most recently from 7f43eeb to 037065f Compare April 18, 2018 16:40
@rbngzlv
Copy link
Copy Markdown
Contributor Author

rbngzlv commented Apr 18, 2018

@Crashillo can you check my css additions, please?

@rbngzlv rbngzlv force-pushed the feature/meeting_services branch 2 times, most recently from 46f16c5 to bbfb839 Compare April 18, 2018 23:08
@rbngzlv rbngzlv force-pushed the feature/meeting_services branch from bbfb839 to 54a239b Compare April 18, 2018 23:18
@rbngzlv
Copy link
Copy Markdown
Contributor Author

rbngzlv commented Apr 19, 2018

@decidim/lot-core ready to review!

@oriolgual oriolgual merged commit 9329b0f into master Apr 19, 2018
@oriolgual oriolgual deleted the feature/meeting_services branch April 19, 2018 07:05
@Crashillo
Copy link
Copy Markdown
Contributor

Sorry my late response! Well actually just 15h later! 😝 It is a couple of things we may enhance, I'll write them down as review comments.
Is it possible to restore the branch, reopen the issue, quick fix, merge, close the issue, remove the branch?? 😇

@rbngzlv
Copy link
Copy Markdown
Contributor Author

rbngzlv commented Apr 19, 2018

Don't worry, I'll made a new PR with your comments. 😄

display: none;
fill: $anchor-color;

&.alert{
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a mixin called modifiers, that you might use to wrap all possibilities (even they're not in use).
Instead of this block, switch it by @include modifiers(fill);. Now, no matter which status you assign to the parent element, the property fill will change accordingly

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Extra tip: I miss $anchor-color is a custom color status, so in that case.... @include modifiers(fill, (alert: $anchor-color)). Now I see again, it's not a big deal, but it's a way to handle statuses in the same way. You'll find other examples in the same file

}
}

.card--list__text--top{
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If this property-modified always comes along with .card--list__text, move it inside that block, and and a &. Like:

.card--list__text {
  ...
  // other properties

  &.card--list__item--top{
     // your properties
  }
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants