Improve PriceData import for better readability

[ObiajuluM]

Currently, to import the PriceData class for building Price Oracle transactions, users need to use the following import statement:

from xrpl.models.transactions.oracle_set import PriceData

This import path is relatively long and can be less intuitive for users already used to the existing model import style. I propose adding a more direct import option.

from xrpl.models import PriceData

I understand this is essentially syntactical sugar, but it would significantly improve the readability and user experience when working with Price Oracle transactions.

Expected Behavior:
The PriceData class should be directly importable from the xrpl.models module.

thanks

[ckeshava]

Hello, thanks for explaining your issue.

I'd like to get the opinions of a few other developers on this topic. I believe PriceData is only used inside OracleSet transaction, this was the motivation for the organization of the code files. I'm not opposed to re-arranging them.

[ObiajuluM]

If this is something you decide to move forward with, the same thing can be applied to Offers