如何正确排序RecyclerView并实现分组带图标效果？

Hey there! Let's get your RecyclerView grouping working exactly as you want it. First, let's address the core issue I suspect you're running into: handling group headers directly in onBindViewHolder() often leads to inconsistent displays (like duplicate headers, missing headers on scroll) and makes your code messy to maintain. Let's walk through the correct approach step by step.

Step 1: Refactor Your Item Data Structure #

First, we need to clearly distinguish between group header items and regular content items. Update your existing Item class (or create separate classes if you prefer) to include a type identifier:

public class PersonItem {
    public static final int TYPE_HEADER = 0;
    public static final int TYPE_CONTENT = 1;

    private int itemType;
    // For header: profession name + icon resource ID
    private String professionName;
    private int professionIconRes;
    // For content: person details
    private String personName;
    private String personInfo;

    // Constructor for header items
    public PersonItem(int itemType, String professionName, int professionIconRes) {
        this.itemType = itemType;
        this.professionName = professionName;
        this.professionIconRes = professionIconRes;
    }

    // Constructor for content items
    public PersonItem(int itemType, String personName, String personInfo) {
        this.itemType = itemType;
        this.personName = personName;
        this.personInfo = personInfo;
    }

    // Getters for all fields
    public int getItemType() { return itemType; }
    public String getProfessionName() { return professionName; }
    public int getProfessionIconRes() { return professionIconRes; }
    public String getPersonName() { return personName; }
    public String getPersonInfo() { return personInfo; }
}

Step 2: Prepare Grouped Data Source #

Before passing data to your Adapter, pre-process it to group by profession and interleave headers with content. This way, your Adapter just needs to bind items in order—no extra logic during binding.

// Assume you have a raw list of Person objects with profession info
List<Person> rawPersonList = getYourRawPersonData();

// Group by profession (use a HashMap to map profession to list of people)
Map<String, List<Person>> groupedByProfession = new HashMap<>();
for (Person person : rawPersonList) {
    groupedByProfession.computeIfAbsent(person.getProfession(), k -> new ArrayList<>()).add(person);
}

// Convert grouped data to a single list of PersonItem (headers + content)
List<PersonItem> finalItemList = new ArrayList<>();
for (Map.Entry<String, List<Person>> entry : groupedByProfession.entrySet()) {
    String profession = entry.getKey();
    int iconRes = getProfessionIcon(profession); // Your custom method to get icon for a profession
    // Add header first
    finalItemList.add(new PersonItem(PersonItem.TYPE_HEADER, profession, iconRes));
    // Add all people in this profession
    for (Person person : entry.getValue()) {
        finalItemList.add(new PersonItem(PersonItem.TYPE_CONTENT, person.getName(), person.getInfo()));
    }
}

// Now pass finalItemList to your Adapter
yourRecyclerViewAdapter.setItems(finalItemList);

Step 3: Update Your Adapter to Handle Multiple Item Types #

Modify your Adapter to create and bind different ViewHolders for headers and content—this keeps your binding logic clean and efficient:

public class PersonAdapter extends RecyclerView.Adapter<RecyclerView.ViewHolder> {

    private List<PersonItem> itemList;

    public PersonAdapter(List<PersonItem> itemList) {
        this.itemList = itemList;
    }

    @Override
    public int getItemViewType(int position) {
        return itemList.get(position).getItemType();
    }

    @Override
    public RecyclerView.ViewHolder onCreateViewHolder(ViewGroup parent, int viewType) {
        LayoutInflater inflater = LayoutInflater.from(parent.getContext());
        if (viewType == PersonItem.TYPE_HEADER) {
            View headerView = inflater.inflate(R.layout.item_profession_header, parent, false);
            return new HeaderViewHolder(headerView);
        } else {
            View contentView = inflater.inflate(R.layout.item_person_content, parent, false);
            return new ContentViewHolder(contentView);
        }
    }

    @Override
    public void onBindViewHolder(RecyclerView.ViewHolder holder, int position) {
        PersonItem item = itemList.get(position);
        if (holder instanceof HeaderViewHolder) {
            HeaderViewHolder headerHolder = (HeaderViewHolder) holder;
            headerHolder.professionIcon.setImageResource(item.getProfessionIconRes());
            headerHolder.professionName.setText(item.getProfessionName());
        } else if (holder instanceof ContentViewHolder) {
            ContentViewHolder contentHolder = (ContentViewHolder) holder;
            contentHolder.personName.setText(item.getPersonName());
            contentHolder.personInfo.setText(item.getPersonInfo());
        }
    }

    @Override
    public int getItemCount() {
        return itemList.size();
    }

    // Header ViewHolder
    static class HeaderViewHolder extends RecyclerView.ViewHolder {
        ImageView professionIcon;
        TextView professionName;

        HeaderViewHolder(View itemView) {
            super(itemView);
            professionIcon = itemView.findViewById(R.id.profession_icon);
            professionName = itemView.findViewById(R.id.profession_name);
        }
    }

    // Content ViewHolder
    static class ContentViewHolder extends RecyclerView.ViewHolder {
        TextView personName;
        TextView personInfo;

        ContentViewHolder(View itemView) {
            super(itemView);
            personName = itemView.findViewById(R.id.person_name);
            personInfo = itemView.findViewById(R.id.person_info);
        }
    }
}

What Was Wrong With Your Original Approach? #

Putting grouping logic directly in onBindViewHolder() is problematic because:

• This method is called every time an item is bound (including during scrolls), so you might end up re-checking group boundaries repeatedly, leading to unnecessary performance overhead.
• It's easy to make mistakes with header visibility (like showing headers multiple times or not showing them when the list is scrolled back up).
• You can't properly reuse ViewHolders for different item types, which defeats RecyclerView's core performance benefit.

With the approach above, we pre-process the data to include headers in the correct positions, and the Adapter just handles each item type cleanly and efficiently.

内容的提问来源于stack exchange，提问作者Hayk Mkrtchyan