Skip to content
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

Feat/add b2b warning topbar inactive org block #13

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Josmar-jr
Copy link
Contributor

What problem is this solving?

Insert a new block called 'b2b-warning-topbar-inactive-organization' to render on top app

How to test it?
Run the b2b-organizations and this repo - Run the vtex-apps/b2b-organizations-graphql#182 - Run the b2b-theme

  1. Access https://josmarjr--b2bstore005.myvtex.com/admin/b2b-organizations/organizations/#/settings
  2. Uncheck "Aprovar automaticamente novas organizações"
  3. Change the color at color picker or/and insert a new message to show at topbar
  4. Save the changes
  5. Access the store and do the login with your account
    [Workspace](Link goes here!)

Screenshots or example usage:

Screenshot 2024-10-17 at 17 27 59 Screenshot 2024-10-17 at 17 28 54

Describe alternatives you've considered, if any.

Related to / Depends on

How does this PR make you feel? 🔗

![](put .gif link here - can be found under "advanced" on giphy)

@vtex-io-docs-bot
Copy link

Beep boop 🤖

I noticed you didn't make any changes at the docs/ folder

  • There's nothing new to document 🤔
  • I'll do it later 😞

In order to keep track, I'll create an issue if you decide now is not a good time

  • I just updated 🎉🎉

Copy link

vtex-io-ci-cd bot commented Oct 17, 2024

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant