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

Why not export rive_core/node.dart in rive.dart? #29

Closed
ptalmeida opened this issue Nov 25, 2020 · 2 comments
Closed

Why not export rive_core/node.dart in rive.dart? #29

ptalmeida opened this issue Nov 25, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@ptalmeida
Copy link

Same as title, why not

export 'package:rive/src/rive_core/node.dart';

in rive.dart so we can access nodes and, per example, change the opacity?

@ptalmeida ptalmeida changed the title Why not export node.dart in ? Why not export rive_core/node.dart in rive.dart? Nov 25, 2020
@luigi-rosso
Copy link
Contributor

Indeed we should! We just haven't gotten to figuring out what the full API access should be. Probably close to everything... we should do this but we want to be cautious so we first exposed little (probably too little).

@HayesGordon HayesGordon added the enhancement New feature or request label Feb 1, 2023
@HayesGordon
Copy link
Contributor

Closing this due to age, and as the API has changed

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

No branches or pull requests

3 participants