Persistence is now happening through the node's filesystem.

┆Issue is synchronized with this Asana task by Unito

• Addition of bundling scripts for component export for module publishing.
• SSO first component for export
• Utilize @rollup/plugin-babel for component library bundling.
• Create rollup.config.js for rollup configuration
• Create babel config for babel integration context
• add main and types properties to package.json

┆Issue is synchronized with this Asana task by Unito

Implementation of VerifyJWS which creates a new JSON Web Signature and returns its value to the caller.
Note: should be implemented within sonr/pkg/dag-jose

Acceptance Criteria

• VerifyJWS should accept a piece of encrypted data and a JWS and be able to assert the validity of the signature.
• Should contain Unit tests to confirm this behavior.
• see the following specification for reference: https://datatracker.ietf.org/doc/html/rfc7515

┆Issue is synchronized with this Asana task by Unito

┆Issue is synchronized with this Asana task by Unito

Update readme with

• Component List
• up and running info for storybook

┆Issue is synchronized with this Asana task by Unito

┆Issue is synchronized with this Asana task by Unito

Is your feature request related to a problem? Please describe.
no

Describe the solution you'd like
Additional testing for existing controls with the following areas in mind
- Check module import for definition (component should be defined)
- Check DOM structure matches implementation in the component implementation.
- Check overrides from props change the expected behaviors / style of the control
- Check call backs are invoked at correct times.

Describe alternatives you've considered
Please describe alternative solutions or features you have considered.

Currently tailwind is set up with a single configuration statically linked in the components barrel export.
Tailwind implementation needs to be updated such that themes are named and components can consume the base tailwind configuration, and extend it's functionality.
Tailwind themes should be swappable through single "Theme" prop on the component .
Example: <Login button theme={"default"}/>

Dependencies once needed for create react app need to be removed

• Removing all unused dev and production dependencies
• Locking dependency versions

Since refactoring the name of this repository to sonr-io/nebula-react the dependency in sonr-io/highway-sdk has become broken. Assuming publishing to npm once renaming the library in package.json will fix this issue.

• Investigate rendering svg components in the context of the virtual DOM
• using jest-dom as a DOM testing harness.

Add eslint config following Airbnb style.

SSO button component should have sonr logo online with button label text.
Position should not be configurable at this time. But should allow for layout resizing to not affect component label orientation.

Is your feature request related to a problem? Please describe.
Please describe the problem you are trying to solve.

• Refactor current component storybook files to use template wrapper for components to allow for generic props to hydrate. Allowing for easier story creation and reuse.
• Components should all have Template implementations allowing for arbitrary props to get passed in to the wrapped component instance. Component should then respect the props that are passed through.

Describe the solution you'd like
Please describe the desired behavior.

Describe alternatives you've considered
Please describe alternative solutions or features you have considered.

Move Prop interface for button component to a types folder sibling to src so they can be published as a type lib.

• addition of @sonr-io/webauthn package within the component library.
• Integration of module within the 'LoginButton' component.
• addition of onError callback within

Creation of test plan with the following cirteria in mind:

• Code coverage
• Component features
  • Individual components should have their own tests
  • dom structure should be asserted on to verify correct behavior (outline what should be asserted on in terms of ids, and tag type)
• CSS matches design goals (see nebula design in notion)

PR submissions should be contingent on the success of react and docz build scripts returning successfully.
Only on the success of both documentation and component builds should a merger be allowed.

Add support for Webauthn module with authentication button

• add startUserLogin registration, with react
  • might be good to use hook, if storybook supports

Overviewg
Highway Methods
These methods interact with a Sonr Highway node which communicates with the underlying blockchain

AccessApp()
InteractObject()
ListenChannel()
LinkDevice()
LinkPeer()
ReadBucket()
ReadObject()
RequestBucket()
RespondBucket()

Sequence
N/A

Resources
https://github.com/sonr-io/sonr/discussions/280

┆Issue is synchronized with this Asana task by Unito

for themes / style definitions for control that are only used within a single control, we should define them scoped to that control specifically.

• create a tailwind configuration with all component specific theme defs and attempt to compile, and bundle them in a single css file linked to the 'index.css'

┆Issue is synchronized with this Asana task by Unito

Currently our WASM build is failing due to some compatibility issues of some of the dependencies.

An example is goleveldb/leveldb, which currently lacks support for WASM, which breaks the build. Other projects face the same issue, such as go-ethereum: ethereum/go-ethereum#16192.

┆Issue is synchronized with this Asana task by Unito

Each supported tail wind override should have it's own mapped property in the sign on buttons component property definition

┆Issue is synchronized with this Asana task by Unito

Overviewg
For querying Schemas in x/schema we should hit the IPFS node for Sonr before returning the result. This would offload the actual resolution of the schema from the Developer.

Sequence
Steps involved in the logic sequence:

1. Refactor QuerySchemaResponse to include SchemaDefinition
2. Call IPFS on query and return data from CID on chain
3. Return QuerySchemaResponse with deserialized SchemaDefinition

Resources
Additional reading to help understand this proposal.

┆Issue is synchronized with this Asana task by Unito

Repository should be exported from create react app.

• Refactor npm scripts to no longer depend on create react app (react-scripts)
• Creation of web pack configuration for storybook

Improve Rollup config to split css and js on the bundling process so people can import js and css separetely

README needs to be updated with the following information:

• Design language (nebula reference)
• version
• usage description
• examples
• development environment standup

┆Issue is synchronized with this Asana task by Unito

┆Issue is synchronized with this Asana task by Unito

Runs the simulation as part of your PR

Changes

• Item 1
• Item 2

API Updates

New Features (required)

Deprecations (required)

Enhancements (optional)

Checklist

• Unit tests
• Documentation

References (optional)

Fixes
Connects

_{Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.}

┆Issue is synchronized with this Asana task by Unito

Fixes issue preventing highway from starting

_{Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.}

┆Issue is synchronized with this Asana task by Unito

Changes

• Removes the auto pass for testing and coverage

API Updates

N/A

New Features (required)

N/A

Deprecations (required)

N/A

Enhancements (optional)

Your tests must now pass.

Checklist

• Unit tests
• Documentation

References (optional)

Fixes
Connects

_{Mention [stepsize] in a comment if you'd like to report some technical debt. See examples here.}

┆Issue is synchronized with this Asana task by Unito

Created UI components should be included within docz 'docs' folder.

Should be named in the following schema
[COMP-NAME].mdx

Should contain all configurable properties and intent of component within definition.

Documentation needed for describing supported styling passed through props.
All generated style definitions from tailwind should be included

We should no longer rely on a style string being passed to the control as a prop, instead we only expose the theme and define the styles for a component with the control.

┆Issue is synchronized with this Asana task by Unito

Storybook will still need a webpack configuration in order to bundle for storybook gallery. Create a webpack definition
See example webpack as reference: https://github.com/joshLong145/graph-art/blob/master/webpack.config.js

• Remove story book dependencies from storybook branch
• Add Gatsby config
• Add DocZRC
• Create docs folder to contain component documentation
• Create doc file for "sso-button"

An improvement over #62

Verify JWK in did/document.go

┆Issue is synchronized with this Asana task by Unito